feat(knowledge): resolution reuse — RCA becomes a reusable ARM asset with Next-Best-Action - #41
Merged
Merged
Conversation
…with Next-Best-Action Closes the ARM feedback loop for root-cause work (IBM Asset-Reuse-Manager: Domain→Category→Asset→ Recommendation→Feedback + "Next Best Action for a Case"). A Resolution asset produced by the RCA pipeline is deposited into the REAL continuum commons (asset_type="resolution", keyed by failure-class), marked reproducible iff it carries the graph digest. When the same failure class recurs, next_best_action() returns the prior resolution to apply — recommendation, not a fresh investigation — and apply_resolution() feeds the ARM reuse loop (commons.record_use) so proven resolutions rank first. Thin adapter over the existing commons.Commons (deposit/search/recommend/record_use) — no parallel store, no island. Demo: deposit the Nix→Guix resolution → a new same-class case finds it → applied → reuse score 1.0. capd caps.knowledge.resolution-reuse; validate + Makefile `reuse` wired. Tests: +6 = 240 tools tests green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Closes the ARM feedback loop for root-cause work — the IBM Asset-Reuse-Manager pattern (Domain → Category → Asset → Recommendation → Feedback) and "Next Best Action for a Case". A Resolution asset produced by the RCA pipeline (the tagged, content-addressed record with the root-cause graph SVG) is now deposited into the real continuum commons, found again when the failure recurs, and reused.
Demo (real): deposit the Nix→Guix resolution → a new same-class case finds it → applied →
reuse {uses:1, evaluations:1, score:1.0}, recommendation"apply Firewall #1 (adr_swap_gate) before authoring in scope".Why it's not an island
Thin adapter over the existing
commons.Commons(deposit/search/recommend/record_use) — no parallel store. Resolutions become first-class, searchable, reusable estate knowledge alongside capabilities/workloads/models.Wired in
capd/resolution-reuse.mesh.capd.json(caps.knowledge.resolution-reuse),validate.py,Makefile reuse.Tests
+6 = 240 tools tests green — deposit is a reproducible resolution asset (declared without a graph digest); Next-Best-Action finds the prior resolution for a failure class and is empty for a genuinely new one; apply records reuse and ranks most-reused first; the lang filter excludes unrelated swaps.
This is the reuse half of the RCA→HellGraph + Resolution-asset pipeline (producer + graph ingest live in prophet-platform#1392; enforcement in source-os#325).
🤖 Generated with Claude Code